Sometimes you may want to use a DNS server for specific domain requests and another DNS server for all other requests. This is helpful, for instance, when connected to a VPN. For hosts behind that VPN you want to use the VPN's DNS server but all other hosts you want to use Google's public DNS. This is called "DNS splitting."
Here, we run dnsmasq as a background service on macOS. The dnsmasq configuration described below implements DNS splitting.
brew install dnsmasq
For years, people have been using jemalloc with ruby. There were various benchmarks and discussions. Legend had it that Jemalloc 5 didn't work as well as Jemalloc 3.
Then, one day, hope appeared on the horizon. @wjordan offered a config for Jemalloc 5.
FROM ruby:3.1.2-bullseye
RUN apt-get update ; \
| export interface DiceResult { | |
| expression: string; | |
| rolls: number[]; | |
| modifier: number; | |
| total: number; | |
| } | |
| /** | |
| * Rolls a standard dice expression. | |
| * |
A pattern for building personal knowledge bases using LLMs.
This is an idea file, it is designed to be copy pasted to your own LLM Agent (e.g. OpenAI Codex, Claude Code, OpenCode / Pi, or etc.). Its goal is to communicate the high level idea, but your agent will build out the specifics in collaboration with you.
Most people's experience with LLMs and documents looks like RAG: you upload a collection of files, the LLM retrieves relevant chunks at query time, and generates an answer. This works, but the LLM is rediscovering knowledge from scratch on every question. There's no accumulation. Ask a subtle question that requires synthesizing five documents, and the LLM has to find and piece together the relevant fragments every time. Nothing is built up. NotebookLM, ChatGPT file uploads, and most RAG systems work this way.
| <!DOCTYPE html> | |
| <html lang="en"> | |
| <head> | |
| <meta charset="UTF-8"> | |
| <meta | |
| name="viewport" | |
| content="width=device-width, initial-scale=1.0" | |
| > | |
| <title>Accessible Tabs</title> |
Audit this Go codebase and aggressively simplify AI-generated, defensive, overly abstract, or unnecessarily generic code.
The goal is to make the code look like it was written by an experienced Go engineer:
| <script lang="ts"> | |
| import { clickOutside } from './clickOutside'; | |
| let open = false; | |
| </script> | |
| <button onclick={() => (open = !open)}> | |
| Toggle menu | |
| </button> |
| import Database from 'better-sqlite3'; | |
| const db = new Database('data.db'); | |
| // Better concurrency for applications with frequent reads. | |
| db.pragma('journal_mode = WAL'); | |
| // SQLite does not enable foreign key constraints by default. | |
| db.pragma('foreign_keys = ON'); |